Release 10.1A: OpenEdge Getting Started:
New and Revised Features
Buttons with images
In Release 10.0B, OpenEdge’s border drawing behavior for buttons that contain images depends on the type of image button—single-image or dual-image. Dual-image buttons use two images (an “up” image and a separate “down” image). Single-image buttons use one image (an “up” image, which is shifted slightly to mimic a “down” appearance for the button).
OpenEdge Release 10.0B creates Windows classic, 3D-style borders for single-image buttons. It does not create any borders for dual-image buttons. For dual-image buttons, you must add borders to the images themselves if you want borders.
In Release 10.1A, you have more options regarding the border drawing behavior for image buttons. In OpenEdge Release 10.1A, the border drawing behavior for image buttons depends on two factors:
- The type of image button (single-image or dual-image).
- The presence of a manifest file—a text file that contains XML code that provides your 4GL application with the look of the Windows XP user interface. By default, the OpenEdge Release 10.1A installation includes the
prowin32.exe.manifestfile in theinstall-dir/bindirectory.In Release10.1A, the default behavior for drawing borders on image buttons is as follows:
Note: This differs from Release 10.0B behavior in that you get a different style border for single-image buttons depending on whether you are using a manifest file.- For single-image buttons, OpenEdge creates a Windows XP-style border (rounded corners, no 3D shadow) when using the manifest file. It draws a Windows classic-style border (angular corners with a 3D shadow) when not using the manifest file.
- For dual-image buttons, OpenEdge does not draw a border for the button by default, regardless of whether there is a manifest file. If you want borders, you must add borders to the images themselves. (This is the same as Release 10.0B behavior.) Alternately, you can change the default behavior to draw borders.
For Release 10.1A, you can specify to change the default border drawing behavior (whereas in Release 10.0B, the default behavior is your only option). To change the default, there is a new
progress.inifile and Registry setting (ButtonImageBorderMode=n) that tells OpenEdge what to do with respect to button image borders. TheButtonImageBorderModesetting goes in the[Startup]section of the Registry orprogress.inifile. It is aprogress.inifile or Registry setting rather than a startup parameter because it is Windows-specific.For details about this new
ButtonImageBorderModesetting and its possible values, see OpenEdge Deployment: Managing 4GL Applications .
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |